Investigation RoadMap
Specs of Instances
...WIP...
This roadmap compares single-node and clustered RabbitMQ behavior. Here, “churn” means repeatedly creating and deleting a resource under load.
RabbitMQ terminology: a connection is a network session; an AMQP channel is a lightweight lane inside it; a queue holds messages for consumers; an exchange routes published messages; and a binding is the routing rule from an exchange to a queue. The Event Exchange publishes broker lifecycle events for observation.
For both Cluster and Single-node, answer the following:
- What's the impact and what can you observe out of:
- high churn of Connection?
- high churn of AMQP channels?
- high churn of Exchanges?
- high churn of Queues?
- high churn of Bindings?
- What can you observe if you enable Event Exchange?
- For each type of binding
- In various types of loads and scenarios
- What are the best use cases for RabbitMQ federation? What can it do across independent brokers?
- What are the limitations of quorum queues? How do they compare with Classic queues?
Share: